Skip to content

Continue tweaking the Kubernetes agent docs for v3#3127

Merged
APErebus merged 7 commits intomainfrom
ap/k8s-scaling
May 1, 2026
Merged

Continue tweaking the Kubernetes agent docs for v3#3127
APErebus merged 7 commits intomainfrom
ap/k8s-scaling

Conversation

@APErebus
Copy link
Copy Markdown
Contributor

@APErebus APErebus commented May 1, 2026

follows on from #3122 to make the docs clearer around the v3 agent

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this page contains all the NFS stuff that's been remove from the other pages

@APErebus APErebus enabled auto-merge (squash) May 1, 2026 06:03
Copy link
Copy Markdown
Contributor

@liam-mackie liam-mackie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some nits, but the main content LGTM

## Custom StorageClass \{#custom-storage-class}

If you need a more reliable storage solution, then you can specify your own `StorageClass`. This `StorageClass` must be capable of `ReadWriteMany` (also known as `RWX`) access mode.
If distribution of script pods across multiple nodes is desired, then you can specify your own `StorageClass`. This `StorageClass` must be capable of `ReadWriteMany` (also known as `RWX`) access mode.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: consider also allowing documenting the use of a non-default RWO storage class. For example:

Suggested change
If distribution of script pods across multiple nodes is desired, then you can specify your own `StorageClass`. This `StorageClass` must be capable of `ReadWriteMany` (also known as `RWX`) access mode.
You may also provide an explicit `StorageClass` to use, if you wish. If the `StorageClass` supports `ReadWriteMany` (also known as `RWX`) as an access mode, the agent will be able to scale past a single node.

Automatic upgrades can be disabled by updating the machine updates settings in your applied [machine policy](/docs/infrastructure/deployment-targets/machine-policies)

## V1
## When do we new major versions
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure what we meant to say here - we should probably reword it

@APErebus APErebus merged commit a33feb6 into main May 1, 2026
5 checks passed
@APErebus APErebus deleted the ap/k8s-scaling branch May 1, 2026 06:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants